Skip to content

chore(main): release 0.19.0 - #89

Merged
sunerpy merged 1 commit into
mainfrom
release-please--branches--main--components--codegraph-rs
Jun 28, 2026
Merged

sunerpy merged 1 commit into
mainfrom
release-please--branches--main--components--codegraph-rs

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.19.0 (2026-06-28)

Features

  • graph: add Godot edge subkind, impact target/verify-plan, orphan confidence (#88) (270a5e6)

This PR was generated with Release Please. See documentation.

@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

sunerpy added a commit that referenced this pull request Nov 19, 2026
Go projects had no Gin, Echo, Fiber, Chi or net/http routes in the
index, and their bare handler and type names had no framework
conventions. A resolver now ports upstream's Go resolver from `go.ts`
as it stands at e8ddc4e2.

Go is detected by a root go.mod that is not empty, indexed or not,
else by an indexed .go file. The root go.mod is already a control
input and a .go file appearing or going is an ordinary change, so no
control kind, lane or marker is added.

Routes are read on comment-stripped text (#89): each call of a verb on
any identifier (#365), Gin's and Echo's GET to HEAD, Chi's and Fiber's
Get to Delete, or net/http's Handle and HandleFunc, is a route that
references the last identifier of its handler. Its first argument must
be URL-shaped (e1f339f, #1308, fixing #1259): a path that starts with
a slash, or on Handle and HandleFunc a Go 1.22 pattern such as
"GET /users/{id}", which names the route's method, so
cache.Put("key", v) is no route. A group's prefix is not applied, as
upstream has no mount pass.

References resolve by upstream's four conventions through the shared
name heuristic (#2225): a function for a name ending in Handler or
starting with Handle, a struct or interface for one ending in Service,
Repository or Store, a function for one ending in Middleware or
starting with Auth or Log, and a type of any kind for a PascalCase
name. These carry the framework halves of #2397 and #2408: an embedded
type is left to name matching and the import resolver, and a
convention guesses only a name written bare, among the declarations of
the reference's own package, its own file first.

Kept Rust behavior, recorded in KNOWN_DIFFS: a tier answers only
through its one candidate, and a convention whose pick declines ends
the chain, where upstream takes the first candidate. In valid Go the
stop changes no result.

Not ported: #2784, which links a conversion such as (*Error)(nil) as a
reference; here it stays a call, promoted to instantiates for a struct.

Two golden corpora change, regenerated with scripts/regen-goldens.sh
--write and logged in docs/equivalence.md: servers gains the route
GET /ping in gin/main.go with its reference to ping, and synthesis
gains GET /users and GET /inline in go/gin/app.go, the first
referencing getUser, while its four edges to the two Discovery structs
keep their targets and confidence and gain the framework's tag.

Precision: 78 of 89 corpora index identically, gf-demo-user among them
(its routes are GoFrame's). The six earlier corpora that detect Go and
change, and the five Go corpora added for this commit, gain every route
an independent mirror of upstream's extraction finds in them; chi has
236, the 212 e1f339f reports plus routes chi's tests added since.
532 references keep their targets and gain the framework's tag, and
338 gain confidence, each in the reference's own package. Two cases go
as upstream's rules go: gin's build-tag twins of Binding leave ten
references to name matching, and thirteen (*T)(nil) interface checks
leave a method named like the type for the render package's struct.

On a CI runner, init, sync and peak memory stay within the performance
lines on gin, prometheus, hotgo, this repository and librechat;
re-syncing gin's routes_test.go, 64 routes, takes 1.04 times as long
as before.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant